release: v1.4.1 — orca runtime-outage detection + ask-timeout contract - #54
Merged
Conversation
Ships #53. orca-wait.sh gains exit 4 so a dead Orca runtime is no longer indistinguishable from a quiet mailbox window, and the worker prompt now requires a timed-out `ask` to be resumed by its message id instead of decided by the worker. Bumps plugin.json and marketplace.json together — the release workflow only gates on plugin.json, so marketplace.json drifts silently when it is left behind. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump only. Ships what landed in #53.
orca-wait.shgains exit 4, so a dead Orca runtime is no longer indistinguishable from a quiet mailbox window. Fires only on an explicit fault (nonzero status,ok:false,connectionLost:true); a normal timeout still checkpoints at 2.askto be resumed by its message id, not decided by the worker.Both
.claude-plugin/plugin.jsonand.claude-plugin/marketplace.jsonare bumped. The release workflow gates only onplugin.json, so marketplace.json drifts silently whenever it is left behind — it has been four releases stale before.Tag
v1.4.1follows once this lands.🤖 Generated with Claude Code